Skip to content

docs(other): add blog post on AI features shipped in May-July and the AI roadmap - #351

Draft
h0pped wants to merge 7 commits into
mainfrom
blog/ai-features-2026-summer
Draft

docs(other): add blog post on AI features shipped in May-July and the AI roadmap#351
h0pped wants to merge 7 commits into
mainfrom
blog/ai-features-2026-summer

Conversation

@h0pped

@h0pped h0pped commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

What/Why/How?

Blog post covering the customer-facing AI features shipped in May-July (Docs MCP, llms.txt, agent discovery, AI Assistant in Reunite) plus the roadmap (Gateway MCP, code mode, custom MCP tools, Maintainer, embeddable AI Assistant).

Also adds Illia Nykonchuk as a blog author (metadata entry + photo).

Do not merge before the next stable Realm release: token refresh, MCP server card / A2A agent card, agent skills, and renderForLlms locale support are currently in 0.136.0-next only.

Reference

Testing

  • All doc links verified against pages in this repo.
  • Feature claims cross-checked against the Realm changelog (0.133.0-0.135.0 stable, 0.136.0-next).

Check yourself

  • Code is linted
  • Tested
  • All new/updated code is covered with tests

Security

  • Security impact of change has been considered
  • Code follows company security practices and guidelines

@h0pped
h0pped force-pushed the blog/ai-features-2026-summer branch from 2880ee8 to ceafac3 Compare July 28, 2026 13:50
@h0pped
h0pped requested review from RomanHotsiy and adamaltman July 28, 2026 14:02
Comment thread blog/ai-features-summer-2026.md Outdated

In just two months, the server got substantially more capable:

- **GraphQL support.** The Docs MCP server is no longer OpenAPI-only. Agents can now list your [GraphQL APIs](https://redocly.com/docs/realm/content/api-docs/add-graphql-docs), browse types, and read whole schemas.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Docs MCP server is no longer OpenAPI-only

This phrase can be misunderstood. I would clarify that the MCP API catalog endpoints now support other apis

- `llms.txt` output now includes **OpenAPI code samples and response samples**, and correctly renders `oneOf` and discriminator schemas: exactly the parts of an API description agents used to trip over.
- Custom Markdoc tags can define their **own LLM rendering** with `renderForLlms`, with locale support. If you built a custom component, its content is no longer invisible to AI.

## An AI Assistant in Reunite that knows your setup, not just our docs

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would expand here that we are dogfooding a support for custom tools which is coming soon and also embedded widget

Comment thread blog/ai-features-summer-2026.md Outdated
Everything above makes your docs something agents can _read_.
The next wave makes them something agents can _act through_:

- **Gateway MCP.** Agents stop just reading about your API and start calling it, with your documentation as the interface. Your docs become the fastest way for any AI tool to integrate with your product.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note that it's opt-in

Comment thread blog/ai-features-summer-2026.md Outdated
- **Code mode.** Instead of a long chain of tool calls, an agent writes a short script that runs in a sandbox and chains the calls itself. Same answers, a fraction of the tokens.
- **Custom MCP tools.** Add your own tools to your project's MCP server, so agents can do what's specific to your product, not only what's built in.
- **Maintainer.** An agent that watches the signals your docs already produce (search queries, feedback, page analytics, support questions), finds the real gaps, validates them and opens pull requests with fixes. Docs that improve while you sleep.
- **Embeddable AI Assistant.** The assistant that answers from your docs, on any website, with a single script tag.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would change "any website" to something like "on your web app"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants